electron refactor symlink and webpack #392
Conversation
|
This is very smart @Kaffiend 👍 👍 👍 |
|
failed because the webpack build expects the stylesheets in the component to be the same as the actual file, not the output file type of CSS after compilation. Going to need to write a helper or custom loader...maybe |
needs index build or its own??
|
@Kaffiend looks like the build has passed - what are your thoughts on this at the moment? |
|
@NathanWalker the build passed but its not ready yet. I need to find some time to get to the last build task and try to understand the custom loader a little better, didnt get to spend much time on it this weekend. The loader is my current obstacle. |
|
Totally understand, loader can be tricky - great effort here. |
|
I havent forgotten about this, just not much time of late. Any help would be much appreciated. |
|
Working on a seed of my own lately and I think with what I've learned with it, I can give this PR a little more love. |
Working on a overhauled concept of the approach the seed has for building electron.
As awesome as this seed is, I feel the electron aspect is in need of some attention, hopefully fully embracing electron's capabilities and simplifying the development process while sharing code base.
I'm attempting to take a similar approach to Electron as was done with Nativescript implementation, as electron is web technology on the desktop, electron is not the web, hopefully this opens things up and makes it easier.
Any help, advice, or insight is most welcome.
I've "speculated" a checklist in an issue on the fork here.